Method, device and system for processing task in device management

ABSTRACT

The present invention provides an improved method, device and system for task processing in a device management. In the present invention, when the current state or the operation of the terminal device is interrupted by an abnormal condition, the improved method includes the steps of checking if any scheduler task exists; prompting the user to select the processing procedure for the scheduler task based on the types of the scheduler task, or processing the impacted scheduler task based on user&#39;s selection or processing the scheduler task based on a predetermined process procedure.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to Chinese Patent Application prioritynumber 200510080264.3, filed Jun. 30, 2005 and to Chinese PatentApplication priority number 200610066651.6, filed Apr. 17, 2006, thedisclosures of which are hereby incorporated herein by reference.

TECHNICAL FIELD

The present invention relates to communication field, and specifically,to an improved method, device and system for processing task in devicemanagement.

BACKGROUND OF THE INVENTION

Currently, as the functions built in a terminal device have beenincreasingly complicated, the possibility of failure in terminaloperating software is dramatically increased. The terminal deviceincludes, but not limited to, the following devices: cell phone,palmtop, notebook computer, embedded device and on-board system. Toeffectively guarantee a good usage experience and the service qualityand to reduce the maintenance costs of the terminal devices, the OpenMobile Alliance (OMA) has set the device management (DM) VI.2specification. The OMA DM VI.2 specification defines a unified standardfor the overall structure, the protocols, the communication terminaldevices and the safety issues for device management.

In the specification, in addition to the synchronous device managementmodel (completing a DM management operation during one session) and theasynchronous device management model (completing a DM managementoperation during multiple sessions), a model of how to schedule tasks isprovided. A Device Management Server (DMS) can set up a task and itstriggering condition, and send them to the terminal device side, so thatthe terminal device can automatically process the DMS managementoperation according to the scheduled time or the condition even when theterminal device is off line. The overall communicating process flowchart for the management operation task between the service device andthe terminal device in the prior art is shown in FIG. 1.

S1. A service device sends an operation notice to a terminal device.

S2. The terminal device establishes a session connection with theservice device.

S3. The service device sets up a management operation task.

S4. The terminal device prompts a user to download the managementoperation task.

S5. The user downloads the management operation task.

S6. The terminal device reports the state of the task.

S7. The service device terminates the session, and sends a sessiontermination message of the management operation task.

S8. The terminal device monitors the processing condition of themanagement operation task in a state that the processing of themanagement operation task may not be interfered with. For example, thestate that the processing of the management operation task may not beinterfered with is a waiting state.

S9. The terminal device processes the management operation task in astate that the processing of the management operation task is notinterrupted.

S10. The terminal device establishes a connection with the servicedevice and reports the state of the processing of the managementoperation task.

S11. The service device terminates the session (or continues to sendanother management command).

Referring to the communicating process flow chart of FIG. 1, theterminal device can monitor the processing of the management operationtask only when it is in a state that the processing of the managementoperation task is not interrupted. However, the terminal device mayrandomly encounter an abnormal condition (such as, the terminal deviceis automatically turned off because the terminal battery runs out, orthe terminal device is automatically turned off at the time set by theterminal user, or the terminal device is turned off due to the user'sinterference); and the occurrence of these abnormities will cause thedownloaded management operation task unable to be triggered andprocessed normally according to the preset triggering conditions.

BRIEF SUMMARY OF THE INVENTION

The present invention provides an improved method, device and system forprocessing tasks in a device management.

With the implementation of the present invention in the terminal device,when the processing of the scheduler task or the operation of theterminal device is interrupted by an abnormal condition, the system willcheck if any management operation task is scheduler and determine thescheduler task to be executed. Based on the executing time limit and thenecessity of the tasks, there are four types of the scheduler tasks, thetype 1 task is the one that doesn't exceed its executing time limit andis not a necessary task to be executed, the type 2 task is the one thatdoesn't exceed its executing time limit and must be executed, the type 3task is the one that has already exceeded its executing time limit andis not a necessary task to be executed, and the type 4 task is the onethat already exceeded its executing time limit but must be executed;

If such a task is scheduler, the system will either prompt the user forhis selection of the processing procedure to process the scheduler task,or process the task based on a predetermined processing procedure, whichincludes: processing the task according to a predetermined procedure setup by the user and processing the task according to a default procedurebuilt in the system.

One of the states in which the processing of the scheduler managementoperation task may be interrupted by an abnormal condition in a terminaldevice is an off state, where the interruption may happen during theoperation of the terminal device, such as the terminal device is in theprocess of being shut down; the terminal device is in the process ofbeing turned on; the terminal device is in the process of adjusting itssystem time.

When a terminal device is in an off state and it reaches the time toprocess a scheduler task, the terminal device will automatically turnitself on, process the scheduler task and turn itself off automatically.Before the terminal device automatically turns itself on, it will checkif it is allowed to be turned on based on a predetermined setting by theuser.

When the operation of the terminal device is transiting from an on stateto an off state, the terminal device uses the actual shutting down timeas a starting time in determining the scheduler task(s) during apredetermined time period.

Once the terminal device is turned on, the system identifies theunexecuted scheduler task(s) during the off time period.

After the terminal device has adjusted its time, it identifies thescheduler task(s) during the jumping time period caused by the timeadjustment.

Before processing the scheduler task, the terminal device evaluates itsown condition to decide if it has resources to process the schedulertask.

Usually, based on the types of the scheduler task, the user has threechoices to process the scheduler task: immediately carrying out theprocessing, delaying the processing, or canceling the processing.

A terminal device management system of the present invention includes adevice management server, sending tasks and receiving processinginformation, and a terminal device, identifying an interrupted schedulertask when the scheduler task is interrupted due to the state of theterminal device or the execution of the terminal device, and processingthe scheduler task based on the processing rules, and transferring theprocessing result to the DM server.

The terminal device includes: a device management task abnormityprocessing module, which establishes and manages a plurality of abnormalcondition procedures, executes the corresponding abnormal conditionprocedures according to the state of the terminal devices or the type ofthe interrupted scheduler task(s), processes the scheduler task based onthe processing rules, and transfers the processing result to the DMserver.

In the device management task abnormity processing module, a processingstrategy for abnormal task can be set to decide if a task execution isabnormal.

The terminal device further includes: a device management taskprocessing module, processing the tasks sent by the device managementserver, reporting execution result, and forwarding an interaction resultsent from the device management task abnormity processing module; adevice management client module, directly exchanging with the devicemanagement server, forwarding the interaction command of the devicemanagement server and the terminal device. The device management taskprocessing module processes the task sent by the device managementserver, including: installing the task, setting the task, monitoring thecondition of the task and controlling the triggering of the task.

The device management server of the present invention includes:

a device management task frame module which sends the task(s) to andreceiving the task execution result(s) from the terminal device.

A terminal device of the present invention includes:

a device management task processing module which processes tasks sentfrom the device management server and reporting the execution resultsback to the device management server;

a device management client module, which interfaces with a user thatcommunicates with the device management server and exchanges informationbetween the device management server and the terminal device;

a device management task abnormity processing module, which monitors aplurality of abnormal conditions based on the predetermined processingrules, and if there is an abnormal condition, processes according to theprocessing rules and transfers the processing result to the devicemanagement server.

The device management task abnormity processing module transfers theinteraction result to the uplink through the device management taskprocessing module and the device management client module, or throughthe device management client module.

The present invention provides an additional fault-proof mechanism in aterminal device. If a user turns on the abnormal-condition-monitoringfunction of the fault-proof mechanism in the terminal device, thefault-proof mechanism starts monitoring the occurrence of the abnormalcondition.

Before an abnormal condition occurs, i.e., when the terminal devicetransits from an on state to an off state, the terminal device will usethe shutting off time as the beginning time and check the schedulermanagement operation task which may be affected and take necessary stepsto prevent any faulty results from happening due to a possibleoccurrence of an abnormal condition.

If the abnormal condition occurs, the terminal device will automaticallyturn on the terminal device at the scheduled processing time, processthe scheduler task and then turn the terminal device off.

If an abnormal condition occurs, especially when the terminal device istransiting from an off state to an on state, or after adjusting itstime, the terminal device checks if there is any scheduler task whichshould be processed, and if there is, processes the scheduler task toremedy the damage caused by the occurrence of the abnormal condition.

Through the implementation of the present invention, the terminal devicewill monitor the processing of the scheduler management operationtask(s) under the abnormal condition. It will process the scheduler taskeither based on the choice of the user or on the default setting of thesystem. The present invention can be implemented into an existing systemand devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overall communicating process flow chart for the managementoperation task between the service device and the terminal device in theprior art;

FIG. 2 is a task processing flow chart of a terminal device whentransiting from an on state to an off state according to an embodimentof the present invention;

FIG. 3 is a task processing flow chart of a terminal device whentransiting from an off state to an on state according to an embodimentof the present invention;

FIG. 4 is a task processing flow chart of a terminal device in an offstate according to an embodiment of the present invention;

FIG. 5 is a schematic of the system according to an embodiment of thepresent invention;

FIG. 6 is a schematic of the system according to an embodiment of thepresent invention.

DETAILED DESCRIPTION OF THE INVENTION

The embodiment of the invention provides an improved method, device andsystem for processing a scheduler task according to its predeterminedtriggering condition under an abnormal condition (the current state oroperation of the terminal device interferes with the processing of thescheduler management operation task). The interruption of processing thescheduler task under the abnormal condition can be divided into twosituations. One is due to the current state of the terminal device andthe other is due to the operation of the terminal device. The operationof the terminal device which causes an interruption is further dividedinto three situations: 1. The terminal device is transiting from an onstate to an off state; 2. The terminal device is transiting from an offstate to an on state; 3. The terminal device is in an on state but hasadjusted its time.

The following examples illustrate the operation of the terminal devicewhich interferes with the processing of the scheduler task.

EXAMPLE 1

A terminal device is transiting from an on state to an off state, whichinterferes with the processing of the scheduler task. The processingsteps are shown in FIG. 2.

S1. Setting the triggering conditions in the terminal device. Thetriggering conditions include:

The condition for detecting the abnormal situation. For example, theelectric quantity of the battery of the terminal device is less than 5%or a pre-defined shut-off time is approaching, or a user is turning offthe terminal device.

The triggering condition of the scheduler task. For example, set a timeperiod of 8 hours for an abnormal condition from the time when theterminal device is turned off. Any tasks scheduled to be processedwithin 8 hours are the tasks to be interfered with.

The processing rules. The processing rules can be based on thepredetermined processing procedure, i.e., the processing rules deliveredby the DM server or pre-set by the user. Or the scheduler tasks can beprocessed based on a user's choice or in a default manner. Theprocessing rules delivered by the DM server includes: processing thetask immediately, delaying to a certain time, or canceling theprocessing, and reporting to the DM server. For example: for a schedulertype 1 task, the user can choose to process the task immediately, ordelay the task to a certain time, or cancel the processing. For ascheduler type 2 task, the user can't choose to cancel the processing.For a scheduler type 3 task, the user can choose to process the taskimmediately or cancel the processing. For a scheduler type 4 task, theuser is not allowed to make any choice, and the terminal device willdirectly process the task based on the default setting. The user of atype 1, 2 or 3 task can also set up a predetermined procedure for thetasks. When the terminal device is processing the task, it will notprompt the user to make a choice again, instead it will process the taskbased on a predetermined procedure set by the user.

S2. A user may choose to activate or not activate the monitoring of thetriggering condition. If the user chooses not to activate the monitoringof the triggering condition, the operation is the same as that in theprior art where the user is not reminded when an abnormal conditionoccurs. If the user chooses to activate the monitoring of the triggeringcondition, the monitoring of the occurrence of the said abnormalcondition is started.

S3. Detecting if there is an abnormal condition, for example, at thetime 18:00 the electric quantity of the terminal device's battery isless than 5% of its total capacity.

S4. In this embodiment of the present invention, the time of 18:00 isused as the starting time to check if any scheduler task is scheduled tobe processed in the following 8 hours. If there is, the relevant task isdetermined as the scheduler task. Obviously, the relevant task can bemore than one.

S5. If there are at least one scheduler tasks, the terminal device willchoose one task to process.

S6. Determining if an input from the user is required in the operationbased on the predetermined triggering condition and the processingrules.

S7. If the user's input is required, the terminal device prompts theuser to select a trigger time for the task. For example, if the chosentask is a type 1 task, the user can choose the task either to beprocessed immediately, or not to be processed, or to be delayed andprocessed at a later time.

S8. If an input from the user is not required, the terminal devicedirectly processes the scheduler task based on the predetermined processrules or the default setting. For example, the task may be processeddirectly.

S9. After the scheduler task is processed upon the user's choice, or isprocessed by the terminal device based on the predetermined processingrules or the default procedure, it is decided if there are any otherscheduler tasks to be processed. If there are, jump to the step ofchoosing one scheduler task to be processed, and continue the processingtherefrom. If there is no more scheduler tasks, i.e. all the schedulertasks have been processed, the terminal device continues its shuttingdown operation.

EXAMPLE 2

The condition under which a terminal device is transiting from an offstate to an on state. FIG. 3 illustrates the processing flow chart.

S1. Setting the triggering condition in the terminal device. Thetriggering condition includes:

The triggering condition for starting checking/monitoring. For example,every time the terminal device is turned on.

The triggering condition for determining the scheduler task. Forexample, the scheduler task, which should be processed, yet has not beenprocessed, is identified during the last period of the off state of theterminal device.

The processing rules. The processing rules include: processing thescheduler task based on the predetermined processing procedure, i.e.,the processing rules delivered by the DM server or pre-set by the user,or processing the scheduler task upon a user's choice or on the defaultprocedure. The processing rules delivered by the DM server include:processing the task immediately, delaying to a certain time, orcanceling the processing, and reporting to the DM server. For example,for a scheduler type 1 task, the user can choose to process the taskimmediately, or delay the task to a certain time, or cancel theprocessing. For a scheduler type 2 task, the user can't choose to cancelthe processing; For a scheduler type 3 task, the user can choose toprocess the task immediately or cancel the processing; For a schedulertype 4 task, the user is not allowed to make any choice, and theterminal device will directly process the task based on the defaultsetting. For the type 1, 2 or 3 task, a user can set up a predeterminedprocedure. Once the procedure is selected, the task is automaticallyprocessed according to the predetermined procedure and the user is notprompted for input.

S2. The user may choose to activate or not to activate the triggeringcondition. If the user chooses not to activate the triggering condition,the scheduler task will be treated in the same way as that in the priorart. When an abnormal condition occurs, the user is not notified. If auser activates the triggering condition, the system starts to monitorthe occurrence of any abnormal condition.

S3. The user turns on the terminal device, for example, the terminaldevice is turned on at 22:00, where it was turned off at 20:00.

S4. Check if there is any scheduler task that should be processed, yethas not been processed in the period from 20:00 to 22:00. There may bemore than one scheduler tasks.

S5. If there are more than one scheduler tasks, one of the schedulertasks to be processed will be selected.

S6. Decide if the user's input is required based on the selectedscheduler task and its triggering condition and the processing rules.

S7. If the user's input is required, the terminal device prompts theuser to choose a triggering time for the task. For example, if thechosen task is a type 1 task and it doesn't exceed its processing time,the user can choose either to process the task immediately, or not toprocess, or delay the processing to a later time. Or if the chosen taskis a type 3 task, i.e., the task has exceeded the last processing timelimit and has not been processed, the user may choose to process thescheduler task immediately or not to process the scheduler task.

S8. If the user's input is not required, the terminal device processesthe task based on the predetermined processing rules and the defaultsetting. For example, the task may be processed directly.

S9. After the scheduler task is processed upon the user's choice, or isprocessed by the terminal based on the predetermined processing rules orthe default procedure, check if there are any other scheduler tasks tobe processed. If there are, jump to the step of choosing one schedulertask to be processed, and continue the process therefrom.

EXAMPLE 3

The scheduler task is interrupted because the terminal device hasadjusted its system time.

S1. Setting the triggering condition in the terminal device. Thetriggering condition includes:

The condition for activating the checking, for example, every time theterminal device adjusts its time.

The triggering condition of the scheduler task. For example, any taskwhich should be processed, yet has not been processed, during thejumping time period or caused by the time adjustment.

(3) The processing rules. The scheduler task is processed based on thepredetermined processing procedure, i.e., the processing rules deliveredby the DM server or pre-set by the user, or the scheduler task isprocessed upon a user's choice or based on the default procedure. The 15processing rules delivered by the DM server include: processing the taskimmediately, delaying to a certain time, or canceling the processing,and reporting to the DM server. For example, for a scheduler type 1task, the user can choose to process the task immediately, or delay thetask to a certain time, or cancel the processing. For a scheduler type 2task, the user can't choose to cancel the processing; For a schedulertype 3 task, the user can choose to process the task immediately orcancel the processing; For a scheduler type 4 task, the user is notallowed to make any choice, and the terminal device will directlyprocess the task based on the default setting. For the type 1, 2 or 3task, the user can also preset a processing procedure, and when the type1, 2 or 3 task is processed, the user will not be prompted for input.The tasks will be automatically processed according to the predeterminedprocessing procedure.

S2. A user may choose to activate or not to activate the triggeringcondition. If the user chooses not to activate the triggering condition,the scheduler task will be processed in the same way as that in theprior art. If an abnormal condition occurs, the user will be notnotified. If the user chooses to activate the triggering condition, theoccurrence of any abnormal condition is monitored.

S3. The system time of the terminal device is adjusted, for example, thesystem time is adjusted from 20:00 to 22:00.

S4.Check if there is any task which should be processed during the timeperiod between 20:00 to 22:00. Obviously there may be more than onescheduler tasks in that period.

S5. If there is at least one scheduler task, the terminal device willchoose one task to process.

S6. Decide if a user's input is required based on the triggeringcondition and the processing rules.

S7. If the user's input is required, the system prompts the user tochoose the triggering time for the task. For example, if the chosen taskis a type 1 task, i.e., it does not exceed its processing time limit,the user can choose either to process the task immediately, or not toprocess the task, or to delay the processing to a later time; or if thechosen task is a type 3 task, i.e., the task that exceeds the lastprocessing time limit and has not been processed, the user can chooseeither to process the task immediately or not to process the task.

S8. If the user's input is not required, the terminal device processesthe scheduler task based on the predetermined processing rules and thedefault setting. For example, the task is processed directly.

S9. After the scheduler task is processed upon the user's choice, or isprocessed by the terminal based on the predetermined processing rules orthe default procedure, check if there are any other scheduler tasks tobe processed. If there are, jump to the step of choosing one schedulertask to be processed, and continue the processing.

EXAMPLE 4

The condition under which the current state of the terminal deviceinterferes with task processing. The flow chart is shown in FIG. 4, andthe steps are as follows:

S1. Setting the triggering condition in the terminal device. Thetriggering condition includes:

The condition for determining an abnormal condition, that is, when thetriggering time for the task is up, the terminal device is in an offstate.

The triggering condition of the scheduler task. The task should beprocessed when the terminal device is in an off state.

The condition for allowing the device to be automatically turned on. Forexample, only when the terminal device is in an airplane mode (a usersets the terminal device off during his flight, usually the airline willnot allow a user to turn on the terminal device), the device is notallowed to be turned on.

The triggering condition on which the scheduler task can be processed.For example, the processing is allowed only when the electric quantityof the battery is above 5% of its capacity, or the signal strength islimited.

The processing rules. The processing rules include: the task isprocessed based on the predetermined processing procedure, that is, theprocessing rules delivered by the DM server or pre-set by the user, orthe scheduler task is processed at a user's choice, or based on thedefault procedure. The processing rules delivered by the DM serverinclude: processing the task immediately, delaying to a certain time, orcanceling the process, and reporting to the DM server. For example, fora scheduler type 1 task, the user can choose to process the taskimmediately, or delay the task to a certain time, or cancel theprocessing. For a scheduler type 2 task, the user can't choose to cancelthe processing; For a scheduler type 3 task, the user can choose toprocess the task immediately or cancel the processing; For a schedulertype 4 task, the user is not allowed to make any choice, and theterminal device will directly process the task based on the defaultsetting. The user of type 1, 2 or 3 task can preset a processingstrategy, such as that the user will not be prompted for an input andthe task will be processed based on a preset processing strategy when atype 1, 2 or 3 task is processed.

S2. A user may choose to activate or not activate the triggeringcondition. If the user chooses not to activate the triggering condition,the operation is the same as that in the prior art; the user is notreminded when an abnormal condition occurs. If the user chooses toactivate the 1-2 triggering condition, the system starts monitoring theoccurrence of the abnormal condition.

S3. When an abnormal condition occurs, for example, a user sets a taskwhich is to report to DMS at 19:00 about the terminal device's currentlocation, while the terminal device is in an off state at 19:00.Obviously there may be more than one task that should be processed at19:00.

S4. The terminal device checks if it is ready to be turned on.

S5. If the user does not activate the airplane mode (no cell phone orother devices can be turned on during the flight), the terminal devicecan automatically be turned on if its battery condition allows.

S6. The terminal device checks if it is ready to process the schedulertask.

S7. Select one scheduler task to be processed if the terminal device'sbattery condition is capable and its signal strength meets theprocessing requirement.

S8. Check if the user's input is required based on the triggeringcondition and the processing rules.

S9. If the user's input is required, the terminal device will prompt theuser to choose the trigger time for the task. For example, if the chosentask is a type 1 task, the user can choose to process the taskimmediately, or not to process the task or to delay the processing to alater time.

S10. If the user's input is not required, the terminal device processesthe task based on the predetermined processing procedure and the defaultsetting. For example, the position information of the terminal device issent directly to DMS.

S11. After the scheduler task is processed upon the user's choice, or beprocessed by the terminal based on the predetermined processing rules orthe default procedure, check if there are any other scheduler tasks tobe processed. If there is, jump to the step of choosing one schedulertask to be processed, and continue to the processing therefrom.Otherwise, the terminal device is automatically turned off.

The OMA DM specification defines DM system's overall structure,protocols and communication mechanism, as well as security in devicemanagement. A terminal device management system is provided in thepresent invention, which is demonstrated through the embodiments of theinvention, through which the terminal device management is achieved byutilizing the DM protocols to send the scheduler task.

The terminal device management system includes: interconnected terminaldevices and a device management server. The device management servercommunicates with the terminal devices through DM protocols.

With reference to FIG. 5, a terminal device further includesinterconnected device management client module, device management taskprocessing module and device management task abnormity processingmodule. A device management server further includes a device managementtask frame module, and the device management task frame modulecommunicates with the device management client module through DMprotocols.

Or, with reference to FIG. 6, the terminal device further includesdevice management task processing module and device management taskabnormity processing module, each connecting separately with the devicemanagement client module. The device management server further includesa device management task frame module; and the device management taskframe module communicates with the device management client modulethrough DM protocols.

The device management task frame module is used to send tasks to theterminal device, and process the interaction result and execution resultsent by the terminal device.

The device management task abnormity processing module is used toprocess the scheduler task which is sent by the device management serverthrough the DM protocols and is transferred by the device managementclient module, and report the execution result to the uplink through thedevice management client module. The scheduler task includes:installing/setting task, monitoring task condition, and controllingtriggering task. The module is also used to transfer the interactionresult sent by the device management task abnormity processing module.

The device management task abnormity processing module is used tomonitor abnormal condition during the execution of a task, based on theexecution condition (including time, event, etc.) of scheduler task setby the terminal device. A processing strategy for abnormal task can beset in the module (for example, if the task has missed the triggeringcondition, the processing is given up, and the result is transferred tothe DM server), and judge if the execution of the scheduler task isnormal or not based on the strategy combined with the executioncondition.

When an abnormal condition occurs, the device management task abnormityprocessing module will process the scheduler task based on thepredetermined processing rules or the default procedure, and transferthe processing result to the device management task processing module.

There are interfaces between the device management task abnormityprocessing module and the device management task processing module,which are used to transfer the processing result to the devicemanagement server through the device management task processing moduleand the device management client module. Or there exist interfacesbetween the device management task abnormity processing module and thedevice management client module, which are used to transfer theprocessing result through the device management client module.

The device management client module, directly exchanging with the devicemanagement server, is used to transfer the interaction command of thedevice management server and terminal device, that is, it is used notonly to transfer scheduler task sent by the device management server tothe device management task processing module, but also to transfer thetask execution result of the device management task processing module tothe device management server; further, it is used to transfer theinteraction result of the device management task abnormity processingmodule to the device management server.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” Words using the singular or pluralnumber also include the plural or singular number respectively.Additionally, the words “herein,” “above,” “below” and words of similarimport, when used in this application, shall refer to this applicationas a whole and not to any particular portions of this application. Whenthe claims use the word “or” in reference to a list of two or moreitems, that word covers all of the following interpretations of theword: any of the items in the list, all of the items in the list and anycombination of the items in the list.

Further, in describing representative embodiments of the presentinvention, the specification may have presented the method and/orprocess of the present invention as a particular sequence of steps.However, to the extent that the method or process does not rely on theparticular order of steps set forth herein, the method or process shouldnot be limited to the particular sequence of steps described. As one ofordinary skill in the art would appreciate, other sequences of steps maybe possible. Therefore, the particular order of the steps set forth inthe specification should not be construed as limitations on the claims.In addition, the claims directed to the method and/or process of thepresent invention should not be limited to the performance of theirsteps in the order written, and one skilled in the art can readilyappreciate that the sequences may be varied and still remain within thespirit and scope of the present invention.

Although the present invention has been fully described in connectionwith the preferred embodiments thereof with reference to theaccompanying drawings, it is apparent to those skilled in the art thatvarious changes and modifications can be made. Such changes andmodifications are intended to be included within the scope of thepresent invention provided that they fall within the scope as defined bythe appended claims and their equivalence.

1. An improved method for task processing in device management,comprising the steps of: determining a scheduler task, when the state ofthe terminal device or an operation of the terminal device interruptsthe processing of the scheduler task; prompting for the user'sselection, and processing the scheduler task based on the selection, orprocessing the scheduler task based on predetermined processing rules.2. The method as claimed in claim 1, wherein the predeterminedprocessing rules include a predetermined processing procedure or adefault processing procedure.
 3. The method as claimed in claim 2wherein the predetermined processing procedure includes: the processingprocedure preset by the Device Management server, or the processingprocedure preset by the user.
 4. The method as claimed in claim 1,wherein the state of the terminal device that may interrupt theprocessing of the scheduler task is that the terminal device is in anoff state; and the operation of the terminal device which may interruptthe processing of the scheduler task includes: the terminal device istransiting from an on state to an off state, or the terminal device isin the state of being turned on, or the terminal device is adjusting itstime.
 5. The method as claimed in claim 4, wherein, when the terminaldevice is in an off state, and the scheduler processing time of thescheduler task is up, the terminal device will be automatically turnedon, and after the scheduler task has been processed the terminal devicewill be turned off.
 6. The method as claimed in claim 5, wherein beforeautomatically being turned on, the terminal device determines if it isallowed to be turned on based on a predetermined setting of the user. 7.The method as claimed in claim 6, wherein before processing the task,the terminal device decides if it has resources to process the schedulertask.
 8. The method as claimed in claim 4, wherein when the operation ofthe terminal device is transiting from an on state to an off state, theterminal device sues the actual shutting down time as a starting time indetermining the scheduler task(s) during a predetermined time period. 9.The method as claimed in claim 4, wherein after the terminal device isturned on, identifying the scheduler task(s) which are not carried outduring the period of the off state.
 10. The method as claimed in claim4, wherein after the terminal device adjusts its time, determining thescheduler task during the jumping time period caused by the timeadjustment.
 11. The method as claimed in claim 1, wherein the user'sselection for processing the scheduler task can be either processing thescheduler task immediately, or canceling the scheduler task or delayingthe processing of the task to a later time.
 12. The method as claimed inclaim 11, wherein corresponding processing procedures are providedaccording to the type of the scheduler task for the user's choice.
 13. Aterminal device management system, which includes a device managementserver, having the capacity of sending a task and receiving the taskexecution information, and a terminal device interacting with the devicemanagement server, comprising: the terminal device identifying theinterrupted scheduler task when the state of the terminal device or theexecution of the terminal device interrupts a scheduler task, andprocessing the scheduler task based on the processing rules, andtransferring the processing result to the DM server.
 14. The system asclaimed in claim 13, wherein the terminal device further comprising:means for establishing and managing a plurality of abnormal conditionprocedures; means for executing the corresponding abnormal conditionprocedures according to the state of the terminal devices or the type ofthe interrupted scheduler task(s); means for processing the schedulertask based on the processing rules, and transferring the processingresult to the DM server.
 15. The terminal device as claimed in claim 14,comprising means for setting the processing rules of the abnormalconditions.
 16. The system as claimed in claim 13, wherein the devicemanagement server further comprises means for managing to send thetask(s) to and receiving the task execution results(s) from the terminaldevice.
 17. The terminal device as claimed in claim 13, comprising:means for processing the received task from a device management server;means for reporting the execution result back to the device managementserver; means for interfacing with a user that communicates with thedevice management server and exchanges information between the devicemanagement server and the terminal device; and means for monitoring aplurality of abnormal conditions based on the predetermined processingrules, and if there is an abnormal condition, processing according tothe processing rules and transferring the processing result to thedevice management server.
 18. The terminal device as claimed in claim17, wherein the means for processing of the abnormal conditions reportsthe user interface result to the device management server and transfersthe processing result to the uplink and the device management clientmodule; or transfers the processing result to the uplink directly. 19.The terminal device as claimed in claim 18, further comprising means forsetting the processing rules of the abnormal conditions in the devicemanagement task abnormity processing module.